.github/workflows/pr-ci.yml (1)

3-8: ⚡ Quick win

Consider whether path-based filtering should apply to push events to main.

The workflow applies the same path-based filtering to push events on the main branch as it does to PRs. This means when a non-Go PR is merged to main, the subsequent push event won't run the full e2e test suite.

Common patterns:

• PR CI: Selective (path-based) to save time and cost ✓
• Post-merge CI (push to main): Comprehensive to ensure main stays green

If the intent is to always validate main comprehensively, consider limiting the path filter to pull_request events only, or running all jobs unconditionally for push events.

Example: Limit filtering to pull_request events only

   changes:
     runs-on: ubuntu-latest
+    if: github.event_name == 'pull_request'
     permissions:
       contents: read

Then update the conditionals on gated jobs:

-    if: needs.changes.outputs.go == 'true'
+    if: github.event_name != 'pull_request' || needs.changes.outputs.go == 'true'

This would skip the jobs on PRs without Go changes, but always run them on push/workflow_dispatch.

Also applies to: 23-29

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/pr-ci.yml around lines 3 - 8, The push event is currently
subject to the same path-based filters as pull_request which prevents full CI
from running after merges to main; update the YAML so path filters (the paths:
/paths-ignore: or paths: entries) apply only under the pull_request trigger and
not under on: push (or alternatively remove path filtering from push so push to
main always runs full jobs); edit the top-level triggers in the workflow to keep
workflow_dispatch and pull_request with the path filter and make push: branches:
[main] unconditional so post-merge pushes always execute the comprehensive e2e
jobs.